How free software developers work
ثبت نشده
چکیده
This configuration leads to questions on the characteristics of the collective action that enables the transition from individual voluntary commitments that are potentially volatile and unstable to the completion of a collective production that involves continuity and sustainability. The production of free software cannot be considered the contingent result of a spontaneous convergence of individual, independent commitments. It presupposes certain forms of motivation for the participants to work, who are in turn capable of ensuring a certain continuity in their commitments and of coordinating the organization of their contributions. Because even if a software program is a text, it is an “active” text that works insofar as it is made up of a list of instructions that are automatically executed by a machine, which requires an extremely strong coherency of the different parts of the text (Horn, 2004).
منابع مشابه
Mobilization of software developers: the free software movement
Free/open source software (F/OSS) development projects are growing at a rapid rate. Globally dispersed virtual communities with large groups of software developers contribute time and effort often without pay. One force behind this phenomenon is the Free Software Movement (FSM), a 20 year-old social movement whose purpose is to promote the use of free software instead of proprietary software. W...
متن کاملReassessing Brooks' Law for the Free Software Community
Proponents of Free Software have argued that some of the most established software engineering principles do not fully apply when considered in an open, distributed approach. Among these principles, “Brooks’ Law” has been questioned in the Free Software context: large teams of developers, contrary to the law, will not need an increasingly growing number of communication channels. As advocates c...
متن کاملSupporting Software Development as Collective Creative Knowledge Work
We view software development as a system of evolution consisting of the three elements: (1) artifacts, (2) individual developers, and (3) a community of developers. An individual’s determining what artifacts to contribute and how, with whom to communicate by asking or answering, and which role to play within the community affects the quality of software to be developed; how the developers relat...
متن کاملConflict Management in an Occupational Community for Free Software Development
In this paper, we present results from the study of how conflict is managed in a globally distributed free software development project. Conflict arises over the use of a nonfree tool to create a GNU Enterprise (GNUe) Website graphic. The GNUe developers resolve the conflict using Internet Relay Chat (IRC), persistent relay chats, threaded email discussions, and community digests. We characteri...
متن کاملApathy Towards the Integration of Usability Work: A Case of System Justification
In this article we report from a case study of a software development organization and we study in particular the developers’ and product managers’ attitudes towards integrating usability work into software development. We offer explanations based on system justification theory illuminating what would-be integrators might be up against. The analysis shows how the developers only pay lip service...
متن کاملPeople Analytics in Software Development
Developers are using more and more different channels and tools to collaborate, and integrations between these tools are becoming more prevalent. In turn, more data about developers’ interactions at work will become available. These developments will likely make People Analytics — using data to show and improve how people collaborate — more accessible and in turn more important for software dev...
متن کامل